Processing method of device information and network device in device information management system

ABSTRACT

In a device information management system in which a management server for managing device information and various devices are connected, a plurality of different types of device information is transmitted to the management server at predetermined timings, respectively. In a device information management system in which a management server for managing device information and various devices are connected, a request to transmit the device information to the management server is transmitted to another device and the device information of the requesting device is transmitted to the management server in accordance with the request.

This application is a divisional of application Ser. No. 11/439,975,filed on May 25, 2006 (now abandoned), which is a divisional ofapplication Ser. No. 09/624,384, filed on Jul. 27, 2000, now U.S. Pat.No. 7,058,705, issued on Jun. 6, 2006.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to a device information management system formanaging device information of each device connected to a network, adevice information managing method, a computer-readable recording mediumin which a device information managing program has been stored, and thedevice information managing program.

2. Related Background Art

Hitherto, in a network system such that a directory server, variousdevices, and various computers are connected and device information ofeach device has been registered in the directory server, the deviceregisters all of its own device information into the directory serverand updates the device information registered in the directory server.

An application of a computer uniformly obtains all of the deviceinformation of the devices to be used from the directory server at sameintervals in the device information registered in the directory server.

SUMMARY OF THE INVENTION

In the above conventional technique, however, since the device registersall of its own device information into the directory server (or updatesall of its own device information registered in the directory server;hereinafter, the registration and updating of the device information arecollectively expressed by “registration”), the device information whichdoes not need to be registered is also transmitted to the directoryserver. There is, consequently, such a problem that there is a waste oftraffic from a viewpoint of a traffic load on the network.

Since the application of the computer uniformly obtains all of thedevice information of the devices to be used at same intervals, all ofthe device information which is not changed or is rarely changed is alsotransmitted to the computer. Thus, there is a problem such that there isa waste of traffic from a viewpoint of a traffic load on the network.

When an abnormality such as power shut-off, trouble, or the like arisesin the device, the device itself cannot perform the updating process ofthe information registered in the directory server. Therefore, there isa problem such that the registered device information and an actualdevice status do not coincide.

The invention intends to solve the problems of the conventionaltechnique mentioned above and it is the first object of the invention toprovide a device information management system and a device informationmanaging method which can reduce a traffic load on a network.

The invention intends to solve the problems which the foregoingconventional technique has and it is the second object of the inventionto provide a device information management system and a deviceinformation managing method in which even in the case where anabnormality such as power shut-off, trouble, or the like arises in thedevice and the device itself cannot update device information registeredin a directory server, a device which can substitute an updating processcan be allowed to update the device information. In such a deviceinformation management system, the registered device information and anactual device status coincide.

The third object of the invention is to provide a control program forcontrolling the foregoing device information management system and arecording medium on which the control program has been stored.

In the device information management system according to the invention,therefore, a plurality of device information of different types istransmitted to the management server at a predetermined timing,respectively.

In the device information management system according to the invention,a request for transmitting device information to the management serveris transmitted to another device and the device information of thedevice which requested is transmitted to the management server inresponse to the request.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing a construction of a device informationmanagement system;

FIG. 2 is a block diagram showing an internal construction of a personalcomputer;

FIG. 3 is a block diagram showing an internal construction of a device;

FIG. 4 is a model diagram of the device information management system;

FIG. 5 is a diagram showing an example of device information which adirectory server has;

FIG. 6 is a flowchart showing the processing operation of an SLPdirectory agent;

FIG. 7 is a flowchart showing the processing operation of an SLP serviceagent;

FIG. 8 is a flowchart showing a registering process of the SLP serviceagent;

FIG. 9 is a flowchart showing the processing operation of an SLP useragent;

FIG. 10 is a flowchart showing a search message generating/transmittingprocess of the SLP user agent;

FIG. 11 is a diagram showing an example of a setup screen of aregistering/updating timing of the device information of the device;

FIG. 12 is a diagram showing an example of a setup screen of a referencetiming of the device information of the user PC;

FIG. 13 is a diagram showing a memory map on a storage medium on whichsoftware of the device information management system according to anembodiment has been stored;

FIG. 14 is a model diagram of a device information management systemhaving a substitute device;

FIG. 15 is a flowchart showing the processing operation of the SLPservice agent;

FIG. 16 is a flowchart showing the processing operation of an SNMPagent;

FIG. 17 is a flowchart showing the processing operation of the SLP useragent;

FIG. 18 is a flowchart showing the processing operation of an SNMPmanager;

FIG. 19 is a diagram showing an example of MIB information;

FIG. 20 is a cross sectional view showing an internal structure of alaser beam printer; and

FIG. 21 is a schematic external view of an ink jet recording apparatusIJRA which can feed a plurality of kinds of papers in correspondence toa print job.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Registration/Updatingof Device Information

According to the invention, in a network system in which a directoryserver, various devices (for example, a peripheral apparatus, a printer,a copying apparatus, a multifunction apparatus, a facsimile apparatus, ascanner), and various computers are connected, device information ofeach device is registered/updated and obtained by the followingprocesses.

(1) The device information which is registered into the directory serveris classified into the following three information.

static information (information which is not changed): for example,device construction information

semistatic information (information which is rarely changed): forexample, device option information

dynamic information (information which is frequently changed): forexample, device status information

(2) An SLP (Service Location Protocol) directory agent exists in thedirectory server. The SLP directory agent manages the device informationof each device connected onto a network.

(3) An SLP service agent exists in the device. The SLP service agentmonitors a status and a situation of the device and registers the deviceinformation into the directory server or updates the device informationon the directory server at the following timing.

When a power source is turned on, the static information, semistaticinformation, and dynamic information are registered into the directoryserver.

In a subsequent stationary state, the semistatic information and dynamicinformation are registered/updated into the directory server at a settiming, respectively.

The registering/updating timing of the device information is set andchanged by the user.

(4) An SLP user agent exists in an application on a computer. The SLPuser agent executes the following processes.

Information in the directory server is searched.

The static information, semistatic information, and dynamic informationare obtained at proper intervals, respectively.

The intervals for obtaining the device information are set by the userevery static information, semistatic information, or dynamicinformation, respectively.

The following operations appear by the above processes.

(1) The device information is classified into the static information,semistatic information, and dynamic information. By constructing in sucha manner that the static information is registered only when the powersource is turned on and is not registered/updated together with thesemistatic information and dynamic information in the stationary state,the static information is not transmitted from the device toward thedirectory server via the network in the stationary state, so that atraffic load on the network is reduced.

(2) The device information other than the static information isclassified into the semistatic information which is rarely changed andthe dynamic information which is frequently changed. By constructing insuch a manner that the semistatic information is not registered/updatedtogether with the dynamic information, the semistatic information is notfrequently transmitted from the device toward the directory server viathe network, so that a traffic load on the network is reduced.

(3) The timings for registering the static information, semistaticinformation, and dynamic information can be set by the user,respectively. Therefore, the device information is individuallyregistered/updated and each device information is registered/updated ata proper timing in a state where a traffic amount of the network issuppressed.

(4) The intervals at which the application on the computer obtains thethree information of the static information, semistatic information, anddynamic information registered in the directory server are properly set,respectively. Thus, since the application does not need tosimultaneously refer to all of the device information, a traffic amountbetween the directory server and the computer is reduced.

An embodiment of the invention will now be described hereinbelow withreference to the drawings.

FIG. 1 is a diagram showing a construction of a network system in whichthe device information management system can operate. In the diagram,reference numeral 101 denotes a color printer; 102 an MFP (MultiFunction Peripheral: a copying apparatus which can be also used as anetwork printer); 103 and 104 monochromatic printers; and 105 a scannerconnected to the network. They are devices which can execute a programof the SLP service agent. Reference numeral 111 denotes a desk-top typepersonal computer (hereinafter, referred to as a desk-top type PC); 112a desk-top type personal computer having a directory server function(hereinafter, referred to as a directory server PC or directory server);113 a notebook-sized personal computer (hereinafter, referred to as anotebook-sized PC); and 120 a fire wall. All of those devices andcomputers can cope with the network.

The desk-top type PC 111 and notebook-sized PC 113 are PCs which canexecute a program of the SLP user agent in the embodiment and inquiredevice information to the SLP directory agent, as will be explainedhereinlater. The directory server 112 is a device which can execute aprogram of the SLP directory agent in the embodiment. As will beexplained hereinlater, the directory server 112 stores informationregarding the devices 101 to 105, accepts an inquiry (obtains thedirectory information) of a search of the user information from thedesk-top type PC 111 or notebook-sized PC 113, and replies the result.

Those devices are connected via a network 100 such as an LAN (Local AreaNetwork) or the like. Those device information has been registered inthe directory server PC 112 by an agent function of each device. Eachdevice can transmit and receive data via the network 100 and providesvarious services.

Among those devices, it is assumed that the color printer 101, MFP 102,monochromatic printer 103, desk-top type PC 111, directory server PC112, and fire wall 120 are installed on the second floor (2F) and themonochromatic printer 104 and scanner 105 are installed on the firstfloor (1F), respectively. Although the notebook-sized PC 113 isconnected to the network 100 from the first floor at present, it can beremoved as necessary.

The network 100 which mutually connects those PCs and devices isconnected to an Internet 130 via the fire wall 120 and also connected toanother network 140 via the Internet 130.

FIG. 2 is a block diagram showing an internal construction of a generalpersonal computer (PC). In the diagram, reference numeral 200 denotes aPC (personal computer) which is equivalent to the desk-top type PC 111,directory server PC 112, or notebook-sized PC 113 in FIG. 1. In the PC200, SLP user agent software (hereinafter, together with SLP serviceagent software which is installed on the device, they are referred to asSLP agent software) is operating.

The PC 200 has a CPU (Central Processing Unit) 201. The CPU 201 executesthe SLP agent software which has been stored in an ROM (Read OnlyMemory) 202 or an HD (Hard Disk) 211 or is supplied from a floppy diskdrive (FD) 212 and integratedly controls each device connected to asystem bus 204.

Reference numeral 203 denotes an RAM (Random Access Memory). The RAM 203functions as a main memory or a work area of the CPU 201. Referencenumeral 205 denotes a keyboard controller (KBC). The KBC 205 controls aninstruction input from a keyboard (KB) 209, a pointing device (notshown), or the like. Reference numeral 206 denotes a CRT (Cathode RayTube) controller (CRTC). The CRT controller 206 controls a display of aCRT display (CRT) 210. Reference numeral 207 denotes a disk controller(DKC). The HD (Hard Disk) 211 and floppy disk drive (FD) 212 stores aboot program, various applications, an edition file, a user file, anetwork management program, and the like. The disk controller 207controls accesses to the HD (Hard Disk) 211 and floppy disk drive (FD)212. Reference numeral 208 denotes a network interface card (NIC). TheNIC 208 performs bidirectional data transmission and reception to/from anetwork apparatus such as a network printer or the like or another PC(Personal Computer) via an LAN (Local Area Network) 220.

In the embodiment, the LAN 220 is substantially the same as the network100 in FIG. 1.

FIG. 3 is a block diagram showing an internal construction of a devicein which the SLP service agent software operates. In the diagram,reference numeral 300 denotes a device which is equivalent to the colorprinter 101, MFP 102, monochromatic printers 103 and 104, or scanner 105in FIG. 1. The device 300 has a CPU (Central Processing Unit) 301. TheCPU 301 executes the SLP agent software which has been stored in an ROM(Read Only Memory) 302 or a hard disk (HD) 311 or is supplied from afloppy disk drive (FD) 312 and integratedly controls each apparatusconnected to a system bus 304.

Reference numeral 303 denotes an RAM (Random Access Memory). The RAM 303functions as a main memory, a work area, or the like of the CPU 301.Reference numeral 305 denotes a user interface controller (UIC). The UIC305 controls a display to a user interface (UI) 309 and an instructioninput from the user interface (UI) 309. Reference numeral 306 denotes afunction controller (FUNCC). The function controller 306 realizes andcontrols a function (FUNC) 310 as a peculiar function of each device.The function controller (FUNCC) is a print engine controller in case ofa printer and a scan engine controller in case of a scanner. Thefunction (FUNC) is a print engine in case of a printer and a scan enginein case of a scanner. The MFP has the function controller (FUNCC) 306and function (FUNC) 310 every function, respectively.

Reference numeral 307 denotes a disk controller (DKC). The hard disk(HD) 311 and floppy disk drive (FD) 312 store various applicationprograms, a data file, a network management program, and the like. Thedisk controller 307 controls accesses to the hard disk (HD) 311 andfloppy disk drive (FD) 312. Reference numeral 308 denotes a networkmodule (NM). The network module 308 performs bidirectional datatransmission and reception to/from another network apparatus or anotherPC (Personal Computer) via an LAN (Local Area Network) 320. In theembodiment, the LAN 320 is substantially the same as the network 100 inFIG. 1.

Since the device can have various constructions, FIG. 3 shows a mereexample.

FIG. 4 is a model diagram of a directory server, a device, and a userpersonal computer (hereinafter, referred to as a user PC) in the deviceinformation management system according to the embodiment. In thediagram, reference numeral 400 denotes an LAN (Local Area Network); 410a user PC; 420 a directory server; and 430 a device. The user PC 410,directory server 420, and device 430 are connected to the LAN 400.

The user PC 410 is equivalent to the desk-top type PC 111 andnotebook-sized PC 113 in FIG. 1. The directory server 420 is equivalentto the directory server 112 in FIG. 1. The device 430 is equivalent tothe color printer 101, MFP 102, monochromatic printers 103 and 104, orscanner 105 in FIG. 1. The LAN 400 is equivalent to the network 100 inFIG. 1.

In the device 430, an SLP service agent 431 issues a registering request(or updating request) of the device information to an SLP directoryagent 422 of the directory server 420 via the LAN 400. The SLP directoryagent 422 registers the device information into a database (DB) 421. AnSLP user agent 411 transmits a searching request or an obtaining requestof the device information in the database (DB) 421 to the SLP directoryagent 422 via the LAN 400. An application 412 receives a search resultand the device information from the SLP user agent 411.

FIG. 5 is a diagram in which an example of the device information whichis stored in the directory server 112 in the device informationmanagement system according to the embodiment is expressed in a tableformat. In the directory server 112, the information in the database(DB) 421 has physically been stored in the hard disk 211.

In FIG. 5, reference numeral 500 denotes directory registrationinformation. The device information regarding one device has been storedin each row of the directory registration information 500. Columns showa device name 501, a network address 502 of the device, a service type503 of the device, attributes (1) 504 to (5) 508 of the device, and anupdatable device address 509.

With respect to the data shown in FIG. 5, for example, the deviceregistered in the second row in the table will be specificallyexplained. A name of this device is “Mr. Color”. A network address ofthis device is “service:prn-clor.canon.co.jp”. The device has a printingfunction and a group which can access this device is “develop”. Thisdevice is installed on the second floor. This device supports a paper ofthe A4 size and a cassette is provided as an option. A status of thisdevice is set to a ready status at present. The updatable devices are“service:prn-clor.canon.co.jp” and “service:admin.canon.co.jp”. Theupdatable device denotes a device which can update the deviceinformation.

The device name 501, network address 502, attribute (1) 504, andattribute (2) 505 correspond to the static information. The attribute(3) 506 and attribute (4) 507 correspond to the semistatic information.The attribute (5) 508 corresponds to the dynamic information.

In the embodiment, the devices of the second to fourth rows shown inFIG. 5 correspond to the color printer 101, MFP 102, and monochromaticprinter 103 in FIG. 1, respectively. The devices of the sixth andseventh rows correspond to the monochromatic printer 104 and scanner 105in FIG. 1, respectively.

The information shown in FIG. 5 is a mere example and further anotheradditional information can exist as information to be stored in thedirectory server 112.

FIG. 6 is a flowchart showing a flow for the processing operation of theSLP directory agent 422 in the device information management systemaccording to the embodiment. The series of processes is executed by theCPU 201 in the directory server 420 in a hardware manner.

In FIG. 6, when the directory server 420 is activated, first in stepS601, a pre-processing of the SLP directory agent 422 is performed.Subsequently, in step S602, whether a packet message from the SLPdirectory agent 422 or SLP service agent 431 has been received or not isdiscriminated.

If it is determined in step S602 that the packet message has beenreceived and this message is a registration message, step S603 followsand the device information is registered in the database 421.

If it is determined in step S602 that the packet message has beenreceived and this message is a search message, step S604 follows and thedevice information in the database 421 is searched.

If it is determined in step S602 that the packet message has beenreceived and this message is an update (delete) message, step S605follows. In step S605, whether the authority (access right) to update(delete) the updating-(deletion-)requested device information exists ornot is discriminated. If it is determined that there is the authority,step S606 follows and the updating/deleting process is executed. If itis determined that there is not the authority, step S606 is skipped andstep S608 follows.

Further, if it is determined in step S602 that the packet message hasbeen received and this message is a message other than the abovemessages, step S607 follows and a process suitable for the other messageis executed.

In step S608, a result of each of the above message process istransmitted to a transmitting source of the message. In step S609,whether the stop of the directory server has been requested (thedirectory server is stopped) or not is discriminated. If it isdetermined in step S609 that the directory server is not stopped, theprocessing routine is returned to step S602 and the apparatus waitsuntil the packet is received again. If it is determined in step S609that the directory server is stopped, step S610 follows and apost-processing of the SLP directory agent is performed. The processingoperation is finished.

FIG. 7 is a flowchart showing a flow for the processing operation of theSLP service agent 431 in the device information management systemaccording to the embodiment. The above series of processes is executedby the CPU 301 in the device 430 in a hardware manner.

In FIG. 7, when the SLP service agent 431 of the device 430 isactivated, first in step S701, a pre-processing of the SLP service agent431 is executed. Subsequently, step S702 follows and the directoryserver 420 is searched. In step S703, whether the directory server 420has been found or not is discriminated. If it is decided in step S703that the directory server 420 is not found, the processing routine isreturned to step S702. If it is determined in step S703 that thedirectory server 420 was found, step S704 follows and the deviceinformation is registered. The details of the registering process of thedevice information in step S704 will be described hereinlater withreference to FIG. 8.

In step S705, whether a request to stop the SLP service agent 431 hasbeen issued (the SLP service agent 431 is stopped) or not isdiscriminated. If it is determined in step S705 that the SLP serviceagent 431 is not stopped, the processing routine is returned to stepS704. If it is determined in step S705 that the SLP service agent 431 isstopped, step S706 follows and a post-processing of the SLP serviceagent is performed and the processing operation is finished.

FIG. 8 is a flowchart showing a flow for the operation of a registeringprocess of the device information in step S704 in FIG. 7.

First, in step S801, whether the timing to register/update the staticinformation has come or not is discriminated. The user of the device 430can set this timing. If it is determined in step S801 that the timing atwhich the static information can be registered/updated has come, theprocessing routine advances to next step S802. The static information isadded to the registration-requested data (or updating-requested data).If it is determined in step S801 that the timing is a timing at whichthe static information cannot be registered/updated, step S802 isskipped and step S803 follows.

In step S803, whether the timing to register/update the semistaticinformation has come or not is discriminated. The user of the device 430can set the timing. If it is determined in step S803 that the timing atwhich the semistatic information can be registered/updated has come,step S804 follows and the semistatic information is added toregistration-requested data (or updating-requested data). If it isdetermined in step S803 that the timing is a timing at which thesemistatic information cannot be registered/updated, step S804 isskipped and step S805 follows.

In step S805, whether the timing to register/update the dynamicinformation has come or not is discriminated. The user of the device 430can set the timing. If it is determined in step S805 that the timing atwhich the dynamic information can be registered/updated has come, stepS806 follows and the dynamic information is added toregistration-requested data (or updating-requested data). If it isdetermined in step S805 that the timing is a timing at which the dynamicinformation cannot be registered/updated, step S806 is skipped and stepS807 follows.

In step S807, a registration message (or update message) is generatedfrom the registration-requested data (or updating-requested data) andtransmitted to the directory server 420. The processing operation isfinished.

In FIG. 8, the static information, semistatic information, and dynamicinformation are added to the registration-requested data in steps S802,S804, and S806, respectively. However, the static information can betransmitted to the directory server 420 in step S802, the semistaticinformation can be transmitted to the directory server 420 in step S804,and the dynamic information can be transmitted to the directory server420 in step S806, respectively.

FIG. 9 is a flowchart showing a flow for the processing operation of theSLP user agent 411 in the device information management system accordingto the embodiment. The series of processes is executed by the CPU 201 inthe device 200 in a hardware manner.

In FIG. 9, when the SLP user agent 411 is activated, first in step S901,a pre-processing of the SLP user agent 411 is executed. Subsequently,step S902 follows and the directory server 420 is searched. In stepS903, whether the directory server 420 has been found or not isdiscriminated. If it is determined in step S903 that the directoryserver 420 is not found, the processing routine is returned to stepS902. If it is decided that the directory server 420 was found, stepS904 follows.

In step S904, whether the packet message has been received or not isdiscriminated. If it is decided in step S904 that the packet message wasreceived and the message is a reply-to-search message, step S905 followsand a receiving process of the reply-to-search message is performed. Ifit is determined in step S904 that the packet message was received andthe message is a message other than the reply-to-search message, stepS906 follows and a process suitable for the other message is executed.If it is decided in step S904 that the packet message is not received,the processing routine directly advances to step S907.

In step S907, whether the presence or absence of a search request (alsoincluding a mere request for obtaining the device information) of thedevice information from the application 412 is discriminated. If it isdetermined in step S907 that there is the search request of the deviceinformation from the application 412, step S908 follows and agenerating/transmitting process of a search message is performed. Thedetails of the generating/transmitting process of a search message instep S908 will be explained hereinlater with reference to FIG. 10.

If it is determined in step S907 that there is not the search request ofthe device information from the application 412, step S908 is skippedand step S909 follows.

In step S909, the presence or absence of a stop request of the SLP useragent 411 (whether the SLP user agent 411 is stopped or not) isdiscriminated. If it is decided in step S909 that the SLP user agent 411is not stopped, the processing routine is returned to step S904. If itis decided in step S909 that the SLP user agent 411 is stopped, theprocessing routine advances to step S910 and a post-processing of theSLP user agent is executed. After that, the processing operation isfinished.

FIG. 10 is a flowchart showing a flow for the operation of thegenerating/transmitting process of the search message in step S908 inFIG. 9.

First, in step S1001, whether the timing for referring to (obtaining)the static information has come or not is discriminated. If it isdetermined in step S1001 that the present timing is the timing forreferring to (obtaining) the static information, step S1002 follows anda search request of the static information is added to the searchrequest. If it is determined in step S1001 that the present timing isnot the timing for referring to (obtaining) the static information, stepS1002 is skipped and step S1003 follows.

In step S1003, whether the timing for referring to (obtaining) thesemistatic information has come or not is discriminated. If it isdetermined in step S1003 that the present timing is the timing forreferring to (obtaining) the semistatic information, step S1004 followsand a search request of the semistatic information is added to thesearch request. If it is determined in step S1003 that the presenttiming is not the timing for referring to the semistatic information,step S1004 is skipped and step S1005 follows.

In step S1005, whether the present time is the timing for referring to(obtaining) the dynamic information or not is discriminated. If it isdetermined in step S1005 that the present timing is the timing forreferring to (obtaining) the dynamic information, step S1006 follows anda search request of the dynamic information is added to the searchrequest for the directory server 420 in step S1007, which will beexplained hereinlater. If it is determined in step S1005 that thepresent timing is not the timing for referring to the dynamicinformation, step S1006 is skipped and step S1007 follows.

In step S1007, the search message is generated from the search requestand sent to the directory server 420. After that, the processingoperation is finished.

There are two kinds of search messages. The first search message is usedto request the getting of the device information of the device whichsatisfies a search equation. The search equation is included in thesearch message. The second search message is used to request the gettingof the device information of the designated device. Information (forexample, the name and the network address of the device) to designatethe device is included in the search message.

For example, if the search equation and the search request of thesemistatic information are included in the search message, thesemistatic information of the device which satisfies the search equationis transmitted to the SLP user agent 411.

Subsequently, a method of setting the timing for registering/updatingthe device information and the timing for referring to (obtaining) itwill be described.

FIG. 11 is a diagram showing an example of a setup screen of theregistering/updating timing of the device information on the displaypanel of the device 430. In the diagram, reference numeral 1100 denotesa setup screen for setting the registering/updating timing of the deviceinformation. The setup screen comprises a column 1101 for displaying atype of information and a column 1102 for displaying theregistering/updating timing. The user changes the registering/updatingtiming on the display panel or by a remote operation.

In the example shown in FIG. 11, the static information is registered atthe time of power-on. The semistatic information is registered into thedirectory server 420 when the power source is turned on and when theconfiguration of the device is changed (for example, when an option isadded). Further, the dynamic information is registered into thedirectory server 420 when the power source is turned on and when thedynamic information is changed (for example, when an error arises, whena status is changed, when there is no paper, when there is not muchtoner left, when the printing operation is started, when the printingoperation is finished, or when an off-line arises).

FIG. 11 shows a mere example. For instance, the registering/updatingtiming can be also set to the timing such as “every 5-minute interval”or the like as shown in FIG. 12.

FIG. 12 is a diagram showing an example of a setup screen which isdisplayed on the display screen of the user PC 410 and used to set thetiming for referring to (obtaining) the device information. In thediagram, reference numeral 1200 denotes a setup screen for setting thetiming for referring to the device information. The setup screencomprises: a device name 1201 for selecting a specific device anddisplaying its name; a column 1202 for displaying a type of information;and a column 1203 for displaying a reference timing. The user changesthe timing for referring to (obtaining) the information type everydevice.

In the example shown in FIG. 12, the user PC 410 issues the searchrequest of the static information for Mr. Color in response to aninstruction of the user, issues one search request of the semistaticinformation every five hours, and issues one search request of thedynamic information every ten minutes.

FIG. 12 shows a mere example. For instance, the reference timing can beset to “not referred to” or the like.

FIG. 13 is a diagram showing a memory map of a CD-ROM as an example of astorage medium. In the diagram, reference numeral 9997 denotes an areawhere a control program (program based on the flowcharts of FIGS. 6 to10) has been stored; 9998 an area where an install program has beenstored; and 9999 an area where the directory information has beenstored.

When the control program is installed into the PC 200, the installprogram stored in the area 9998 where the install program has beenstored is first loaded into the system and executed by the CPU 201.Subsequently, the install program which is executed by the CPU 201 readsout the control program from the area 9997 where the control program hasbeen stored and installs it onto the hard disk 211.

The invention can be applied to a system comprising a plurality ofapparatuses (for example, host computer, interface equipment, reader,and the like) or an integrated apparatus or can be also applied to anapparatus comprising one equipment.

Naturally, the object of the invention is accomplished by a methodwhereby a storage medium on which program codes (control program) ofsoftware to realize the functions of the embodiment mentioned above havebeen stored is supplied to a system or an apparatus and a computer (aCPU or an MPU) of the system or apparatus reads out and executes theprogram codes stored in the storage medium.

In this case, the program codes themselves read out from the storagemedium realize the novel functions of the invention and the storagemedium in which the program codes have been stored constructs theinvention.

As for the storing apparatus according to the embodiment, the computerreads out and executes the control program stored in the storage medium,so that the functions of the embodiment mentioned above are realized.However, the invention is not limited to it but also incorporates a casewhere an OS (Operating System) or the like which is operating on thecomputer executes a part or all of the actual processes on the basis ofinstructions of the control program and the functions of the embodimentmentioned above are realized by those processes.

For example, a floppy disk, a hard disk, an optical disk, a magnetoopticdisk, a CD-ROM (Compact Disk Read Only Memory), a CDR (Compact DiskRecordable), a magnetic tape, a non-volatile memory card, an ROM chip,or the like can be used as a storage medium for supplying the programcodes.

Further, the program codes read out from the storage medium are writteninto a memory equipped for a function expanding board inserted in acomputer or a function expanding unit connected to the computer, andafter that, a CPU or the like equipped for the function expanding boardor function expanding-unit executes a part or all of the actualprocesses, and the functions of the embodiment mentioned above can berealized by those processes.

Obviously, the invention can be also applied to a case where the programcodes of software to realize the functions of the embodiment mentionedabove are stored in a storage medium and the program codes aredistributed from the storage medium to a requester via a communicationline such as personal computer communication or the like.

According to the device information management system of the inventionas described in detail above, there are effects such that the device canefficiently register/update the device information with the load of thenetwork suppressed and the user PC can efficiently monitor the deviceinformation in a real-time manner with the load of the networksuppressed.

According to the storage medium of the invention, there is an effectsuch that the device information management system of the invention canbe smoothly controlled.

<Substitution of Registration of Device Information>

In the device information management system in FIG. 4, the device 431itself transmits the registration message or updating message to thedirectory server 420. However, when a power shut-off or troubles occurin the device 430, there is a situation such that the device 430 itselfcannot transmit the registration message or updating message. Therefore,a device information management system having a device for updating thedevice information in place of it (hereinafter, such a device isreferred to as a substitute device) will now be described.

An SLP service agent and an SNMP (Simple Network Management Protocol)agent exist in a device (printer or the like) of the device informationmanagement system having the substitute device. The device executes thefollowing processes at the time of power-on.

A search request is issued to the directory server and the substitutedevice (personal computer or the like) is searched (however, thesubstitute device includes an SNMP manager function and can collect thedevice information of the device without using the directory server. Thesubstitute device also includes an SLP user agent and can transmit thesearch message or updating message to the directory server.)

SNMP_TRAP is transmitted to the detected substitute device and a requestfor the substitution is tried.

When the request for substitution is accepted to the substitute device,the device notifies the substitute device of the substituting conditionsand updating contents. The substituting conditions show in which statethe substitute-requested device makes the substitute-device execute asubstitution process. The updating contents show which deviceinformation should be updated by the substitute device. The substitutingconditions and the updating contents are notified by the SNMP. Thesubstituting conditions are defined by an enterprise MIB (ManagementInformation Base).

A permission of an access to the directory server is set so that thesubstitute device can change the device information registered in thedirectory server.

An SLP user agent and an SNMP manager exist in the substitute device(personal computer or the like). The substitute device executes thefollowing processes.

The search/updating of the device information to the directory server isperformed.

A status change of the substitute-requested device is monitored by usingthe SNMP.

When the updating of the device information registered in the directoryserver is substitute-requested from the device, the device informationregistered in the directory server is updated in place of the device inaccordance with the substituting conditions.

An embodiment of the invention will now be described hereinbelow withreference to the drawings.

FIG. 14 is a model diagram of a directory server, a device, a userpersonal computer (user PC), and a substitute-device in the deviceinformation management system having the substitute device according tothe embodiment. The directory server 420 and user PC 410 are equivalentto those in FIG. 4.

In the diagram, reference numeral 1440 denotes a substitute device. Thesubstitute device 1440 corresponds to the desk-top type PC 111 inFIG. 1. The substitute device 1440 has an SNMP manager 1441 and an SLPuser agent 1442.

The device 430 further has an SNMP agent 1432.

The SNMP agent 1432 and SNMP manager 1441 can monitor the device statusand perform a TRAP notification by an SNMP protocol.

FIG. 15 is a flowchart showing the processing operation of the SLPservice agent 431 in the device information management system accordingto the embodiment. In the diagram, first in step S1501, the SLP serviceagent 431 executes a pre-processing of the SLP service agent.Specifically speaking, the opening of a port for transmitting andreceiving data to/from the other device, the obtaining of a necessarymemory, the initialization of other variables, and the like are executedby an SLP protocol.

Subsequently, in step S1502, the directory server 420 on the network issearched. This search is executed by a service request of an SLP packet.In step S1503, whether the directory server 112 has been found or not isdiscriminated. When the directory server 420 exists on the network,there is a reply to the service request and the SLP service agent 431can obtain a network address of the directory server 420.

When there is no reply to the service request of the SLP packet, it isdetermined that the directory server 112 cannot be found. The processingroutine is returned to step S1502.

When there is a reply to the service request of the SLP packet, it isdetermined that the directory server 420 was found. The processingroutine advances to step S1504. In step S1504, the device information isregistered into the database 421 of the directory server 421.

After the initial registration of the device information, the presenceor absence of the substitute device on the network is discriminated instep S1505 in order to prepare for the case where the device itselfcannot update the registered information due to the occurrence of anabnormality such as power shut-off, troubles, or the like in the device.In the embodiment, the SLP service request (search message) istransmitted to the searched directory server 420 so as to search thedevice having the SNMP agent 1441.

Whether the substitute device has been found or not is discriminated instep S1506. When it is decided that the substitute device was found (inthe case where there is a row of the device name “snmp admin” in thedirectory registration information 500 in FIG. 5), step S1507 follows.In step S1507, a request event (substitute request event) is notified tothe SNMP agent 1432, thereby allowing the SNMP agent 1432 to transmitSNMP_TRAP of the substitute request to the substitute device 1440.

Whether a result (request event result) for SNMP TRAP has been receivedfrom the SNMP agent 1432 or not is discriminated in step S1508. When itis determined that the request event result was received, step S1509follows. In step S1509, whether the request has been accepted or not isdiscriminated. When it is determined that the request was accepted, stepS1510 follows. In step S1510, the substitute device also registers thedevice information so that the device information registered in thedatabase 421 can be updated (deleted). Specifically speaking,“service:admin.canon.co.jp” is added to the updatable device address 509in the directory registration information 500 in FIG. 5.

In step S1511, the device information in the directory server 112 isupdated by the device itself in accordance with a change in devicestatus. Specifically speaking, the registering/updating process of thedevice information is executed in accordance with a flowchart of FIG. 8.In next step S1512, the substitute device is searched again at apredetermined period in order to prepare for a case where the substitutedevice cannot be searched or a case where the request is not acceptedalthough the substitute device can be searched. In step S1512, whetherthe time to search the substitute device (predetermined period) has comeor not is discriminated. If it is determined that the time to search thesubstitute device came, the processing routine is returned to stepS1505. If it is determined that the present time is not the time tosearch the substitute device, the processing routine advances to stepS1513.

In step S1513, whether the SLP service agent 431 is stopped or not isdiscriminated. If it is determined that the SLP service agent 431 is notstopped, the processing routine is returned to step S1511. If it isdetermined that the SLP service agent 431 is stopped, the processingroutine advances to step S1514. In step S1514, a post-processing of theSLP service agent is performed. Specifically speaking, the closure ofthe port, the opening of the memory, and the like are executed.

FIG. 16 is a flowchart showing the processing operation of the SNMPagent 1432 in the device information management system according to theembodiment.

First, in step S1601, the SNMP agent 1432 executes a pre-processing.Specifically speaking, the opening of the port to transmit and receivedata to/from the other device, the obtaining of a necessary memory, theinitialization of other variables, and the like are executed by an SNMPprotocol. In step S1602, whether the event or SNMP message has beenreceived or not is discriminated. If it is determined that the requestevent from the SLP service agent 431 was received, step S1603 follows.In step S1603, SNMP_TRAP for allowing the designated substitute deviceto update the device information is transmitted. After that, step S1609follows. In the embodiment, a reply to SNMP_TRAP for the substituterequest is returned by the SNMP message.

If it is determined in step S1602 that the SNMP message was received,step S1604 follows. In step S1604, whether the SNMP message received instep S1602 is the reply message from the substitute device or not isdiscriminated. If it is determined that it is the reply message from thesubstitute device, step S1605 follows. In step S1605, the reply resultis MIB registered (message process) as information regarding thesubstitute device. In the MIB registration, “anotherManager” and“anotherManagerNetworkAddress” are registered in accordance with adefinition shown in FIG. 19, which will be explained hereinlater.

In step S1606, subsequently, the request event result (result indicatingwhether the request was accepted or not) is notified to the SLP serviceagent 431. In step S1608, a reply process to the SNMP message isperformed. After that, step S1609 follows.

If it is decided in step S1604 that the SNMP message is not the replymessage from the substitute device, step S1607 follows. In step S1607, aprocessing for the other SNMP messages is performed. Step S1608 follows.

In step S1609, whether the SNMP agent 1432 is stopped or not isdiscriminated. If it is determined that the SNMP agent 1432 is notstopped, the processing routine is returned to step S1602. If it isdetermined that the SNMP agent 1432 is stopped, the processing routineadvances to step S1610. In step S1610, a post-processing is executed.Specifically speaking, the closure of the port, the opening of thememory, and the like are executed.

FIG. 17 is a flowchart showing the processing operation of the SLP useragent 1442 in the device information management system according to theembodiment.

First, in step S1701, the SLP user agent 1442 executes a pre-processing.Specifically speaking, the opening of the port to transmit and receivedata to/from the other device, the obtaining of a necessary memory, theinitialization of other variables, and the like are executed by the SLPprotocol. In step S1702, subsequently, the directory server 420 on thenetwork is searched. This search is executed in response to a servicerequest of the SLP packet. In step S1703, whether the directory server420 has been found or not is discriminated. When the directory server420 exists on the network, there is a reply to the service request andthe SLP user agent 1442 of the printer device can obtain the networkaddress of the directory server 420. If there is no reply to the servicerequest of the SLP packet, it is determined that the directory server420 is not found yet. The processing routine is returned to step S1702.

When there is the reply to the service request of the SLP packet, it isdetermined that the directory server 420 was found. The processingroutine advances to next step S1704. In step S1704, whether aregistration updating (deleting) event or an SLP command from the SNMPmanager 1441 has been received or not is discriminated. If it isdetermined that the registration update (delete) event from the SNMPmanager 1441 was received, step S1705 follows. In step S1705, the SNMPmanager 1441 is controlled so as to obtain the device information fromthe device 431, and the registration message or updating message is sentto the SLP directory agent 422 in order to register or update the deviceinformation on the basis of the device information obtained from thedevice 431. At this time, a registering process similar to that in theflowchart shown in FIG. 8 is executed.

If it is determined in step S1704 that the SLP command was received,step S1706 follows. In step S1706, a searching process (for example, thesearch message is sent to the SLP directory agent 422) is performed inaccordance with the SLP command. The processing result is transmitted innext step S1707.

In step S1708, whether the SLP user agent 1442 is stopped or not isdiscriminated. If it is determined that the SLP user agent 1442 is notstopped, the processing routine is returned to step S1704. If it isdetermined that the SLP user agent 1442 is stopped, step S1709 follows.A post-processing is executed in step S1709. Specifically speaking, theclosing of the port, the opening of the memory, and the like areexecuted.

FIG. 18 is a flowchart showing the processing operation of the SNMPmanager 1441 in the device information management system according tothe embodiment.

First, in step S1801, the SNMP manager 1441 executes a pre-processing.Specifically speaking, the opening of the port to transmit and receivedata to/from the other device, the obtaining of a necessary memory, theinitialization of other variables, and the like are executed by the SNMPprotocol. In step S1802, whether the event has been received or not isdiscriminated. If it is determined that the event was received and itindicates the TRAP reception, step S1803 follows. In step S1803, whetherthe event obtained in step S1802 is SNMP_TRAP for the substitute requestor not.

If it is determined that the obtained event is SNMP_TRAP for thesubstitute request to the directory server 420, step S1805 follows. Instep S1805, whether the status of the substitute requesting device 430can be monitored or not (whether the designated device can be monitoredor not by SNMP) is discriminated by using the SNMP protocol. Thisdiscrimination can be performed by transmitting the command by the SNMPprotocol to the network address of the substitute requesting device.

Subsequently, whether the monitoring by SNMP of the designated device ispossible or not is discriminated in step S1806. If it is determined thatthe monitoring by SNMP of the designated device is possible, step S1807follows. In step S1807, an SNMP message indicative of the substituteacceptance is sent to the substitute requesting device. If it isdetermined in step S1806 that the monitoring by SNMP of the designateddevice is impossible, step S1808 follows. In step S1808, an SNMP messageindicative of the substitute rejection is sent.

If it is determined in step S1803 that the obtained event is notSNMP_TRAP indicative of the updating substitute of the deviceinformation registered in the directory server 420, step S1804 follows.In step S1804, another TRAP processing is executed.

If it is determined in step S1802 that the event was received and itindicates the command reception, step S1809 follows. In step S1809,whether the event obtained in step S1802 indicates a monitor command ofthe substitute requesting device or not is discriminated. If it isdetermined that the obtained event indicates the monitor command of thesubstitute requesting device, step S1811 follows and the device ismonitored. Subsequently, in step S1812, whether the substituterequesting device is normally operating or not is discriminated. If itis determined that the device is not normally operating (abnormal), nextstep S1813 follows. In step S1813, the updating (deleting) event of thedevice information registered in the directory server 420 is notified tothe SLP user agent 1442.

If it is decided in step S1809 that the obtained event is not themonitor command, step S1810 follows and a processing for other commandsis executed.

If it is determined in step S1812 that the substitute requesting deviceis normally operating, step S1813 is skipped and step S1814 follows.

A reply process to the command is performed in step S1814.

Whether the SNMP manager 1441 is stopped or not is discriminated in stepS1815. If it is determined that the SNMP manager 1441 is not stopped,the processing routine is returned to step S1802. If it is determinedthat the SNMP manager 1441 is stopped, the processing routine advancesto step S1816. A post-processing is executed in step S1816. Specificallyspeaking, the closing of the port, the opening of the memory, and thelike are performed.

FIG. 19 is a diagram showing an example of MIB information forrequesting the substitution in the device information management systemaccording to the embodiment. In the embodiment, “anotherManager”,“deviceCondition”, “anotherManagerAction”, and“anotherManagerNetworkAddress” are defined as information regarding thesubstitute device.

According to the device information management system according to theembodiment, the computer reads out and executes the control programstored in the storage medium, so that the functions of the embodimentmentioned above are realized. However, the invention is not limited tosuch an embodiment but naturally also incorporates a case where an OS(Operating System) or the like which is operating on the computerexecutes a part or all of the actual processes on the basis ofinstructions of the control program and the functions of the embodimentmentioned above are realized by those processes.

The control program according to the invention can be loaded into the PC200 shown in FIG. 2 or onto a device that is equivalent thereto from anexternal storage medium via a storage medium or a network such asE-mail, personal computer communication, or the like and executed. Theinvention can be also applied to such a case.

For example, a floppy disk, a hard disk, an optical disk, a magnetoopticdisk, a CD-ROM (Compact Disk Read Only Memory), a CD-R (Compact DiskRecordable)), a magnetic tape, a non-volatile memory card, an ROM chip,or the like can be used as a storage medium for storing the controlprogram.

As described in detail above, according to the device informationmanagement system of the invention, even in the case where anabnormality such as power shut-off, troubles, or the like arises in thedevice and the device itself cannot update the registration information,the substitute device can be allowed to update the registrationinformation and there is an effect such that the actual device status ismatched with the registered device information.

According to the storage medium of the invention, there is an effectsuch that the foregoing device information management system of theinvention can be smoothly controlled.

A laser beam printer can be mentioned as an example of the printer. FIG.20 is a cross sectional view showing an internal structure of the laserbeam printer (hereinafter, abbreviated to LBP). The LBP can inputcharacter pattern data or the like and print it onto a recording paper.

In FIG. 20, reference numeral 2840 denotes an LBP main body for formingan image onto the recording paper as a recording medium on the basis ofa supplied character pattern or the like; 2800 an operation panel onwhich switches for operation, an LED display, and the like are arranged;and 2801 a printer control unit for controlling the whole LBP 2840 andanalyzing character pattern information or the like. The printer controlunit 2801 converts mainly the character pattern information into a videosignal and outputs it to a laser driver 2802.

The laser driver 2802 is a circuit for driving a semiconductor laser2803 and on/off switches a laser beam 2804 which is emitted from thesemiconductor laser 2803 in accordance with an inputted video signal.The laser beam 2804 is swung right and left by a rotary polygon mirror2805 and scans on an electrostatic drum 2806. Thus, an electrostaticlatent image of a character pattern is formed on the electrostatic drum2806. The latent image is developed by a developing unit 2807 around theelectrostatic drum 2806 and, thereafter, the developed image istransferred onto the recording paper. Cut sheets are used as recordingpapers. The cut sheet recording papers are enclosed in a plurality ofsheet cassettes 2808 corresponding to a plurality of kinds of papersloaded in the LBP 2840, conveyed into the apparatus by a paper feedroller 2809 and conveying rollers 2810 and 2811, and supplied to theelectrostatic drum 2806.

An ink jet printer can be also mentioned as an example of the printer.FIG. 21 is a schematic external view of an ink jet recording apparatusIJRA which can feed a plurality of kinds of papers (not shown) incorrespondence to a print job.

In the diagram, a lead screw 5005 rotates via driving force transfergears 5011 and 5009 in an interlocking relational manner with theforward/reverse rotation of a driving motor 5013. A carriage HC which iscome into engagement with a spiral groove 5004 of the lead screw 5005has a pin (not shown) and is reciprocated in the directions shown byarrows a and b. An ink jet cartridge IJC is mounted on the carriage HC.Reference numeral 5002 denotes a paper pressing plate for pressing thepaper onto a platen 5000 in a range corresponding to the movingdirection of the carriage. Reference numerals 5007 and 5008 denotephotocouplers serving as home position detecting means for confirmingthe existence of a lever 5006 of the carriage in a region where thephotocoupler is arranged and performing the switching of the rotatingdirection of the motor 5013, or the like. Reference numeral 5016 denotesa member for supporting a cap member 5022 for capping the front side ofa recording head; and 5015 sucking means for sucking the air in the capand performing a sucking and a recovery of the recording head via anopening 5023 in the cap. Reference numeral 5017 denotes a cleaning bladeand 5019 indicates a member for enabling the cleaning blade to be movedin the forward/backward direction, and those component elements aresupported to a main body supporting plate 5018. The blade is not limitedto a shape shown in the diagram but a well-known cleaning blade can beobviously applied to the invention. Reference numeral 5021 denotes alever to start the sucking in the sucking/recovery operation. The lever5021 is moved in association with the movement of a cam 5020 adapted tobe come into engagement with the carriage. A driving force from thedriving motor is transferred by well-known transfer means such as clutchswitching or the like. The capping, cleaning, and sucking/recovery areconstructed in such a manner that a desired process can be performed ata corresponding position by the operation of the lead screw 5005 whenthe carriage reaches an area on the home position side. However, if adesired operation is performed at a well-known timing, the invention canbe applied to any construction.

1. A network device that communicates with a server apparatus and sendsa write request to the server apparatus without receiving a request fromthe server apparatus, said network device comprising: a request unitconstructed to make a request for registering, updating or deletingdevice information of said network device in a predetermined area of theserver apparatus, an access right being required to write into thepredetermined area; a specifying unit constructed to specify asubstitute device that registers, updates or deletes the deviceinformation of said network device; and a setting unit constructed toset the access right such that the substitute device specified by saidspecifying unit is enabled to register, update or delete the deviceinformation of said network device in the predetermined area of theserver apparatus.
 2. A network device according to claim 1, wherein thespecified substitute device registers, updates or deletes the deviceinformation of said network device when said network device cannotupdate the device information.
 3. A network device according to claim 1,further comprising a detection unit constructed to detect an abnormalitythat has occurred in said network device, wherein the specifiedsubstitute device registers, updates or deletes the device informationof said network device when said detection unit detects the abnormality.4. A network device according to claim 3, wherein the abnormality is apower shut-off status.
 5. A network device according to claim 3, whereinthe abnormality is a trouble.
 6. A network device according to claim 1,wherein when a device accepts registering or updating the deviceinformation of said network device, said specifying unit specifies thedevice as the substitute device.
 7. A server apparatus for communicationwith a network apparatus that sends a write request to said serverapparatus without receiving a request from said server apparatus, saidserver apparatus comprising: a reception unit constructed to receive arequest for registering, updating or deleting device information of thenetwork device in a predetermined area of said server apparatus, anaccess right being required to write into the predetermined area; adiscrimination unit constructed to discriminate, based on the requestreceived by said reception unit, whether the network device hasauthority to register, update or delete the device information of thenetwork device in the predetermined area of said server apparatus; andan execution unit constructed to register, update or delete the deviceinformation of the network device in the predetermined area of saidserver apparatus, based on the request received by said reception unit,if said discrimination unit discriminates that the network device hasthe authority.
 8. A server apparatus according to claim 7, furthercomprising an informing unit constructed to inform execution resultsprovided by said execution unit.
 9. A computer implemented method for anetwork device that communicates with a server apparatus and sends awrite request to the server apparatus without receiving a request fromthe server apparatus, comprising: a processor performing the steps of: arequest step of requesting to register, update or delete deviceinformation of said network device in a predetermined area of the serverapparatus, an access right being required to write into thepredetermined area; a specifying step of specifying a substitute devicethat registers, updates or deletes the device information of saidnetwork device; and a setting step of setting the access right such thatthe substitute device specified by said specifying step is enabled toregister, update or delete the device information of said network devicein the predetermined area of the server apparatus.
 10. A methodaccording to claim 9, wherein the specified substitute device registers,updates or deletes the device information of said network device whensaid network device cannot update the device information.
 11. A methodaccording to claim 9, further comprising a detection step of detectingan abnormality that has occurred in said network device, wherein thespecified substitute device registers, updates or deletes the deviceinformation of said network device when said detection step detects theabnormality.
 12. A method according to claim 11, wherein the abnormalityis a power shut-off status.
 13. A method according to claim 11, whereinthe abnormality is a trouble.
 14. A method according to claim 9, whereinwhen a device accepts registering or updating the device information ofsaid network device, said specifying step specifies the device as thesubstitute device.
 15. A computer implemented method for a serverapparatus for communication with a network apparatus that sends a writerequest to said server apparatus without receiving a request from saidserver apparatus, comprising: a processor performing the steps of: areception step of receiving a request for registering, updating ordeleting device information of the network device in a predeterminedarea of said server apparatus, an access right being required to writeinto the predetermined area; a discrimination step of discriminating,based on the request received by said reception step, whether thenetwork device has authority to register, update or delete the deviceinformation of the network device in the predetermined area of saidserver apparatus; and an execution step of executing to register, updateor delete the device information of the network device in thepredetermined area of said server apparatus, based on the requestreceived by said reception step, if said discrimination stepdiscriminates that the network device has the authority.
 16. A methodaccording to claim 15, further comprising an informing step of informingexecution results provided by said execution step.
 17. Acomputer-readable storage medium on which is stored a computer programthat implements a method for a network device that communicates with aserver apparatus and sends a write request to the server apparatuswithout receiving a request from the server apparatus, said methodcomprising: a request step of requesting to register, update or deletedevice information of said network device in a predetermined area of theserver apparatus, an access right being required to write into thepredetermined area; a specifying step of specifying a substitute devicethat registers, updates or deletes the device information of saidnetwork device; and a setting step of setting the access right such thatthe substitute device specified by said specifying step is enabled toregister, update or delete the device information of said network devicein the predetermined area of the server apparatus.
 18. Acomputer-readable storage medium on which is stored a computer programthat implements a method for a server apparatus for communication with anetwork apparatus that sends to a write request to said server apparatuswithout receiving a request from said server apparatus, said methodcomprising: a reception step of receiving a request for registering,updating or deleting device information of the network device in apredetermined area of said server apparatus, an access right beingrequired to write into the predetermined area; a discrimination step ofdiscriminating, based on the request received by said reception step,whether the network device has authority to register, update or deletethe device information of the network device in the predetermined areaof said server apparatus; and an execution step of executing toregister, update or delete the device information of the network devicein the predetermined area of said server apparatus, based on the requestreceived by said reception step, if said discrimination stepdiscriminates that the network device has the authority.